Digital media privacy protection

ABSTRACT

In one example of digital media privacy protection, a computer-readable medium stores computer-executable instructions that, when executed, cause one or more processors to execute operations including capturing at least one image file, obfuscating at least all facial images included in the captured image file, comparing all facial images included in the captured image file against a locally stored privacy policy, unobfuscating those of the facial images included in the captured image file for which the comparison against the locally stored privacy policy results in a positive match, and rendering the captured image file.

CROSS-REFERENCE TO RELATED APPLICATION

The present application is a Continuation of U.S. application Ser. No.13/882,491 filed Apr. 29, 2013, which is the U.S. National PhaseApplication under 35 U.S.C §371 of PCT Application Serial No.PCT/US12/50894 filed on Aug. 15, 2012, the disclosures of which arehereby incorporated herein by reference in their entirety.

TECHNICAL FIELD

The implementations and embodiments described herein pertain generallyto protecting the privacy of individuals amidst ubiquitous digital mediavenues.

BACKGROUND

Presently, there is an increasing number of online, and even offline,venues in which pictures and video feeds may be published, often inreal-time. With cloud-computing resources, including social mediaservices, providing the infrastructure support for this surge inspontaneous publishing of digital media, the potential for an individualto have his/her image published in a public venue increases withregularity, often with limited opportunities to protect his/her ownprivacy.

SUMMARY

In one example embodiment, a computer-readable medium storescomputer-executable instructions that, when executed, cause one or moreprocessors to execute operations including capturing at least one imagefile, obfuscating at least all facial images included in the capturedimage file, comparing all facial images included in the captured imagefile against a locally stored privacy policy, unobfuscating those of thefacial images included in the captured image file for which thecomparison against the locally stored privacy policy results in apositive match, and rendering the captured image file.

The foregoing summary is illustrative only and is not intended to be inany way limiting. In addition to the illustrative aspects, embodiments,and features described above, further aspects, embodiments, and featureswill become apparent by reference to the drawings and the followingdetailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

In the detailed description that follows, embodiments are described asillustrations only since various changes and modifications will becomeapparent to those skilled in the art from the following detaileddescription. The use of the same reference numbers in different figuresindicates similar or identical items.

FIG. 1 shows an example system configuration in which digital mediaprivacy protection may be implemented, arranged in accordance with atleast some embodiments described herein;

FIG. 2 shows an example configuration of a client device by whichdigital media privacy protection may be implemented, arranged inaccordance with at least some embodiments described herein;

FIG. 3 shows an example configuration of a cloud-based service providerfor implementing digital media privacy protection, arranged inaccordance with at least some embodiments described herein;

FIG. 4 shows an example processing flow for implementing digital mediaprivacy protection, arranged in accordance with at least someembodiments described herein;

FIG. 5 shows an alternative example processing flow for implementingdigital media privacy protection, arranged in accordance with at leastsome embodiments described herein; and

FIG. 6 shows a block diagram illustrating an example computing device bywhich various example solutions described herein may be implemented,arranged in accordance with at least some embodiments described herein.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part of the description. In thedrawings, similar symbols typically identify similar components, unlesscontext dictates otherwise. Furthermore, unless otherwise noted, thedescription of each successive drawing may reference features from oneor more of the previous drawings to provide clearer context and a moresubstantive explanation of the current example embodiment. Still, theexample embodiments described in the detailed description, drawings, andclaims are not meant to be limiting. Other embodiments may be utilized,and other changes may be made, without departing from the spirit orscope of the subject matter presented herein. It will be readilyunderstood that the aspects of the present disclosure, as generallydescribed herein, and illustrated in the Figures, can be arranged,substituted, combined, separated, and designed in a wide variety ofdifferent configurations, all of which are explicitly contemplatedherein.

FIG. 1 shows an example system configuration 100 in which digital mediaprivacy protection may be implemented, arranged in accordance with atleast some embodiments described herein. As depicted, configuration 100may include a client device 105; digital media subjects 102 a, 102 b, .. . , 102 n; and a cloud-based service/data provider 110. Further, acommunication link 107 may refer to a communication link enabled by aprotocol utilized to transmit data and/or information between a clientdevice 105 and service/data provider 110.

Subjects 102 a, 102 b, . . . , 102 n may refer to persons of whomdigital media images potentially may be captured by client device 105,and for whose privacy is sought to be protected by the embodiments ofdigital media privacy protection described herein. Unless otherwisestated herein, reference to subjects 102 a, 102 b, . . . , and 102 n mayhereafter be substituted by a collective reference to “subjects 102.”Regardless, in a broad sense, subjects 102 may refer to the generalpublic. On a more practical level, subjects 102 may refer toacquaintances, friends, family members, or other people known by or inthe vicinity of the entity that owns or exercises control over clientdevice 105. Such entity may be a person who owns or exercises controlover client device 105. Alternatively, such entity may be, e.g., asecurity company, a news agency, an independent news gatherer (i.e., ablogger), a store owner, etc. These examples are not intended to belimiting, but rather to illustrate the numerous possibilities forentities that may own and/or exercise control over client device 105.

Client device 105 may refer to any device with the capability toacquire, collect, and/or manipulate digital media files, includingphotographic images and/or videos. Examples of such devices include (butare not limited to) the following: camera-equipped smartphones, tabletcomputing devices, laptop computers, set-top boxes (i.e., gamingconsole) having a camera built-in or attached as an accessory, andnon-laptop computer configurations, all of which may be connected to theaforementioned mobile communications network or, alternatively, to awired network.

Client device 105 may be configured to send one or more photos, videos,or other forms of visual digital media captured or acquired thereby tocloud-based service/data provider 110.

Communications for client device 105 may be implemented by a wirelessservice provider (not shown), which may also be known as a mobilenetwork carrier, wireless carrier, or even cellular company. Regardlessof the alternate reference, the wireless service provider may provideservices for mobile communications subscribers. Client device 105 may beconfigured to communicate with service/data provider 110, other suchclient devices whether or not such devices are subscribed to theservices of the wireless service provider, and/or a third-party entity.

Service/data provider 110 may refer to a cloud-based storage anddissemination platform owned and/or operated by a third-party serviceprovider. Service/data provider 110 may include a framework of hardware,software, firmware, or any combination thereof, to which, e.g., captureddigital media files may be stored or from which one or more captureddigital media files may be shared with subscribers to the hostedservice. Thus, service/data provider 110 may be implemented as atelecommunications service provider and/or web-based storage and sharingservice to which user of client device 105 registers prior to use. Suchregistration may include pre-configuration of user preferences orsettings for sharing captured digital media files, text posts,purchasing applications for client device 105; soliciting orcontributing data, information, and/or captured digital media files fromor to service/data provider 110; etc. Accordingly, in an exemplaryembodiment, service/data provider 110 may be a social networkingservice. Further, service/data provider 110 may relay data 111including, at least, a privacy policy or a dynamic update to an existingprivacy policy by which digital media privacy protection may beimplemented on client device 105.

Data 111, as set forth above, may include a privacy policy or a dynamicupdate to an existing privacy policy for implementing digital mediaprivacy protection. Thus, data 111 may include a database, pertaining tosubjects 102, of permissions regarding digital media files, e.g.,photographs and/or videos, captured by client device 105. Therefore,data 111 may include a database of names of subjects 102, photographicand/or video images and corresponding names of subjects 102, andpermissions (e.g., full, conditional, or denied) for one or more ofsubjects 102. The permission for each of subjects 102 may include one ormore levels of authorization for that particular one of subjects 102 toallow at least a facial image of that subject to be included orotherwise identified in a photograph or video image captured by clientdevice 105.

Alternatively, or in addition, data 111 may include a database,pertaining to various ones of subjects 102 from whom authorization hasbeen granted to allow at least a facial image thereof to be included orotherwise identified in a photograph or video image captured by clientdevice 105.

Regardless, data 111 stored at client device 105 and/or service/dataprovider 110 may be dynamic, and subject to change by submissions madeby one or more of subjects 102, by client device 105, or by some othersource (e.g., event organizer).

Servers 112 a, 112 b, . . . , and 112 n may refer to servers hosted byor for service/data provider 110. More particularly, servers 112 a, 112b, . . . , and 112 n may be the access point at which data 111 may bereceived from one or more of subjects 102, client device 105, or someother source (e.g., event organizer), via communication link 107.Further, data 111 on one or more of servers 112 may be accessed by ortransmitted to client device 105, via communication link 107. Unlessotherwise stated herein, reference to servers 112 a, 112 b, . . . , and112 n may hereafter be substituted by a collective reference to “servers112.”

Communication link 107 may include any mobile communications technology,e.g., GSM, CDMA, etc., depending upon the technologies supported byparticular wireless service providers to whose services client device105 and service/data provider 110 may be assigned or subscribed.Further, the aforementioned communication link 107 may be implementedutilizing non-cellular technologies such as conventional analog AM or FMradio, Wi-Fi™, wireless local area network (WLAN or IEEE 802.11),Worldwide Interoperability for Microwave Access (WiMAX™), Bluetooth™,hard-wired connections, e.g., cable, phone lines, and other analog anddigital wireless voice and data transmission technologies.

Thus, in FIG. 1, configuration 100 provides an example, though notexclusive, environment by which the privacy for each of myriad potentialsubjects of whom a digital image is captured by client device 105 may beprotected.

FIG. 2 shows an example configuration 200 of a client device by whichdigital media privacy protection may be implemented, arranged inaccordance with at least some embodiments described herein. As depictedin FIG. 2, client device 105 may include an operating system (OS)configuration 205 of various components or modules, e.g., implemented bya framework of hardware, software, firmware, or any combination thereof.Such software and/or firmware may include one or more computer-readablemedia including but not limited to Application Specific IntegratedCircuit (ASIC) or Customer Specific Integrated Circuit (CSIC). Thevarious components or modules corresponding to OS configuration 205 mayinclude, but are not limited to, an image capturing component 210, anobfuscation component 215, a facial recognition component 220, a policycomponent 225, and a rendering component 230. Further, OS configuration205 is not limited to such components or modules, as obviousmodifications may be made by adding further components or modules oreven eliminating at least one of the components or modules describedhere or even by having various components or modules assuming rolesaccorded to other components or modules in the following description. Asfurther depicted in FIG. 2, the various components or modulescorresponding to policy component 225 may include, but are not limitedto, a face database 235, a permissions component 240, and a serverintegration component 245.

Image capturing component 210 may refer to a framework of hardware,software, firmware, or any combination thereof, that is configured,designed, and/or programmed to capture digital media files, includingphotographs and/or video files. Thus, image capturing component 210 maybe included in any device having the capability to acquire, collect,and/or manipulate digital media images and/or videos to implement someaspect of the techniques discussed herein. Accordingly, image capturingcomponent 210 may be included in, though not exclusively: a smartphone,a tablet computing device, a laptop computer, a set-top box (i.e.,gaming console or accessory), and non-laptop computer configurations,any of which may be connected to the aforementioned mobilecommunications network or, alternatively, to a wired network.

Obfuscation component 215 may refer to a component or module that isconfigured, designed, and/or programmed to obfuscate, or otherwise blur,at least all discernible facial images included in a digital media filecaptured by image capturing component 210. Such obfuscation may occurupon the capturing of a digital media file or upon review of a storedprivacy policy. For the purposes of the embodiments described herein, adiscernible facial image may be any facial image within a photograph orvideo image frame captured by image capturing component 210. Therefore,any facial image having discernible features may be obfuscated, orotherwise, blurred by obfuscation component 215.

Obfuscation, in accordance with the embodiments described herein, mayutilize known blurring techniques. For example, but not as a limitation,discerned facial images may be targeted for Gaussian blurring, forapplication of known blurring tools or techniques, or for pixelmanipulation. Other known and even foreseeable techniques may beutilized by the embodiments herein, and digital media privacy protectionis not to be limited by implementation of the obfuscation or blurringtools and techniques utilized therefor.

In addition obfuscating, or otherwise blurring, all discernible facialimages in a digital media file captured by image capturing component210, obfuscation component 215 may further be trained, reconfigured,redesigned, and/or reprogrammed to further obfuscate, or otherwisefurther blur, other features found in a digital media file. Non-limitingexamples of such features may include corporate logos, clothing brandsor images, product placements, vulgar imagery, etc.

Facial recognition component 220 may refer to a framework of hardware,software, firmware, or any combination thereof, that is configured,designed, and/or programmed to discern any facial image within a digitalmedia file, e.g., photograph or video image frame, captured by imagecapturing component 210 for comparison against facial images included ina locally stored database of facial images, i.e., data 111 as accessedby policy component 225. Facial recognition component 220 may recognizeand compare the discernible facial images from the photograph or videoimage frame captured by image capturing component 210 before or inparallel with the obfuscation of the aforementioned photograph or videoimage frame by obfuscation component 215.

Policy component 225 may refer to a component or module that isconfigured, designed, and/or programmed to access data 111 stored ateither client device 105 or service/data provider 110 to determinewhether a facial image included in a particular photograph or video filethat is discerned by facial recognition component 220 may beunobfuscated for any of the reasons pertaining to the privacy policy forthe respective one of subjects 102 corresponding to the discerned facialimage.

As set forth above, the various components or modules corresponding topolicy component 225 may include, but are not limited to, face database235, permissions component 240, and server integration component 245.

Face database 235 may refer to a compilation of digital media images,including photographs and video image frames, of one or more of subjects102 a, 102 b, . . . , 102 n, who have submitted full or conditionalpermission or who have denied permission to have their personal image,as captured by client device 105, rendered. The personal image, asapplicable to the embodiments described herein, includes at least afacial image for the respective one of subjects 102. The permission forthe respective one of subjects 102 may be modified to apply to otheraspects of the subject's personal appearance, as may be captured byclient device 105.

Permissions component 240 may refer to a component or module that isconfigured, designed, and/or programmed to access data 111, whetherstored locally on client device 105 or on one of servers 112 onservice/data provider 110.

For each of subjects 102 captured in a particular digital media file byclient device 105, before or in parallel with obfuscation component 215obfuscating all discernible facial images, the facial image discerned inthe digital media file by facial recognition component 220 and matchedto a corresponding image in face database 235 may be compared to thepermissions accessed by permissions component 240.

In accordance with various embodiments of digital media privacyprotection, the accessed permissions granted by one or more of subjects102 may be full, partial/conditional, or denied. By granting fullpermission, a respective one of subjects 102 may allow all correspondingdigital media images captured by client device 105 to be stored,transferred, and/or shared with at least the facial image of therespective one of subjects 102 being unobfuscated, i.e., not blurred.However, facial images of one or more remaining subjects in a commondigital media image may remain obscured or blurred, depending upon thecorresponding permissions given.

By granting partial, contingent, or otherwise conditional permission, arespective one of subjects 102 may allow corresponding digital mediaimages captured by client device 105 to be stored, transferred, and/orshared with the facial image of the respective one of subjects 102 beingunobfuscated, i.e., not blurred, under certain circumstances. Forinstance, conditional permission may apply to a particular geographiclocation, e.g., in a particular office setting, at a particularrestaurant, at a particular sporting event, etc. In addition or as analternative, conditional permission may further apply to particular timesetting, e.g., on Christmas day, on February 14, next Saturday, etc.Further still, conditional permission may further apply to both locationand time, e.g., during this year's association convention, on Christmasmorning at your house, on February 14 at this restaurant, etc. Ofcourse, there are many other permutations of time, location, and othervariables that may be utilized to provide partial, contingent, orotherwise conditional permission for a respective one of subjects 102 tohave respective facial images captured by client device 105 rendered, inaccordance with various embodiments of digital media privacy protectiondescribed herein.

By denying permission, a respective one of subjects 102 may prevent anydigital media image captured by client device 105 to be rendered, inaccordance with various embodiments of digital media privacy protectiondescribed herein, without the facial image of the respective subjectobfuscated or otherwise blurred.

Further, data 111 may be finite. That is, in some embodiments, data 111is not capable of including permissions, whether full, conditional, ordenied, of the entire general public, which is the entirety of potentialsubjects 102. Thus, by default, permission for rendering is denied forany subject whose facial image is captured by client device 105 in adigital media file and whose permission is not included in data 111 oris otherwise not accessible by permissions component 240.

Accordingly, the embodiments of digital media privacy protection areable to protect the privacy of, at least, unwitting, unwilling, and/orunaware subjects of digital media images or files captured by clientdevice 105.

Server integration component 245 may refer to a component or module thatis configured, designed, and/or programmed to access data 111, or anyupdates thereto, from service/data provider 110 by client device 105;and to provide updates to data 111, stored on service/data provider 110,from client device 105. That is, in accordance with various embodimentsof digital media privacy protection described herein, the permissionsaccessed by permissions component 240 are dynamic in nature, and any oneof the permissions, whether full, conditional, or denied, may be changedby a respective one of subjects 102 using a corresponding client deviceor by having client device 105 update the respective permission includedin data 111.

Rendering component 230 may refer to a component or module that isconfigured, designed, and/or programmed to remove any restrictionsconfigured to prevent a particular captured image from being storedlocally on client device 105 and/or on servers 112 at service/dataprovider 110; remove any restrictions configured to prevent a particularcaptured image from being transmitted to another device or storagemedium; and/or remove any restrictions configured to prevent aparticular captured image from being uploaded to a cloud-basednetworking entity, e.g., a social networking service. More particularly,rendering component may render, as indicated above, a digital mediaimage captured by client device 105, with an unobfuscated facial imagefor just those subjects 102 for whom permission has been granted, withinthe context therefore.

Thus, FIG. 2 shows example OS components of client device 105 that maybe utilized in protecting privacy for subjects of digital media imagesand files, in accordance with various embodiments described herein.

FIG. 3 shows an example configuration 300 of a cloud-based serviceprovider for implementing digital media privacy protection, arranged inaccordance with at least some embodiments described herein.Configuration 300 may include various components or modules, e.g.,implemented by one or more computer-readable media including but notlimited to ASIC or CSIC, hosted on one or more of servers 112. Thevarious components or modules may include, at least, a server policycomponent 305, a dynamic policy component 310, and a client integrationcomponent 315. Further, configuration 300 is not limited to suchcomponents or modules, as obvious modifications may be made by addingfurther components or modules or even eliminating at least one of thecomponents or modules described here or even by having variouscomponents or modules assuming roles accorded to other components ormodules in the following description.

Server policy component 305 may refer to a component or module that isconfigured, designed, and/or programmed to serve as a counterpart topolicy component 225. Thus, server policy component 305 may access data111, whether stored locally on a respective one of servers 112 or onclient device 105. In accordance with various embodiments of digitalmedia privacy protection, server policy component 305 may accesspermissions that grant full or partial/conditional permission to havecorresponding digital media images captured by client device 105rendered, i.e., stored, transferred, and/or shared with the facial imageof the respective one of subjects 102 being unobfuscated. Alternatively,the server policy component 305 may access a prohibition, or denial, ofsuch rendering of a corresponding digital media image.

Dynamic policy component 310 may refer to a component or module that isconfigured, designed, and/or programmed to integrate updates topermissions into data 111. That is, the permissions accessed by serverpolicy component 305 are dynamic in nature, and any one of thepermissions, whether full, conditional, or denied, may be changed by arespective one of subjects 102 using a corresponding client device or byhaving client device 105 transmit at least one updated permission toservice/data provider 110 to thereby update data 111.

Client integration component 315 may refer to a component or module thatis configured, designed, and/or programmed to synchronize any updates todata 111, which may be received from multiple sources, with policycomponent 225 on client device 105.

Accordingly, FIG. 3 shows configuration 300 that facilitates digitalmedia privacy protection on service/data provider 110.

FIG. 4 shows an example processing flow 400 for implementing digitalmedia privacy protection, arranged in accordance with at least someembodiments described herein. Processing flow 400 may includesub-processes executed by various components that are part of clientdevice 105 and/or service/data provider 110. However, processing flow400 is not limited to such components, as obvious modifications may bemade by re-ordering two or more of the sub-processes described here,eliminating at least one of the sub-processes, adding furthersub-processes, substituting components, or even having variouscomponents assuming sub-processing roles accorded to other components inthe following description. Processing flow 400 may include variousoperations, functions, or actions as illustrated by one or more ofblocks 405, 410, 415, and/or 420. Processing may begin at block 405.

Block 405 (Capture Digital Image) may refer to image capturing component210 on client device 105 capturing at least one digital media file,including at least one still photograph and/or one or more video files,which may or may not include one or more of subjects 102. Processing mayproceed from block 405 to block 410.

Block 410 (Obfuscate (at least) All Facial Images) may refer toobfuscation component 215 obfuscating, or otherwise blurring, at leastall discernible facial images included in the one or more digital mediafiles captured by image capturing component 210. As previouslyindicated, a discernible facial image may be any facial image within astill photograph or video image frame captured by image capturingcomponent 210. Thus, any facial image in the one or more captureddigital media files having discernible features may be obfuscated, orotherwise, blurred by obfuscation component 215. Further, in at leastone embodiment, block 410 may also refer to the obfuscation or blurringof other features found in the one or more captured digital media files.Non-limiting examples of such features may include corporate logos,clothing brands or images, product placements, vulgar imagery, etc.Processing may proceed from block 410 to block 415.

Block 415 (Compare Facial Images to Privacy Policy) may refer to facialrecognition component 220 discerning any facial image within the one ormore digital media files captured by image capturing component 210 forcomparison against facial images included in a locally stored databaseof facial images, i.e., data 111 as accessed by policy component 225.Facial recognition component 220 may recognize and compare thediscernible facial images from the photograph or video image framecaptured by image capturing component 210 before or in parallel with theobfuscation of the facial images included in the one or more captureddigital media files by obfuscation component 215. Block 415 may furtherinclude policy component 225 accessing data 111 stored at client device105 and/or service/data provider 110 to determine whether a particularfacial image included in the captured particular photograph or videofile that is discerned by facial recognition component 220 may beunobfuscated in view of the respective privacy policies for subjects102. Processing may proceed from block 415 to block 420.

Block 420 (Render Captured Image File) may refer to rendering component230, for those of subjects 102 who have granted permission within thecontext of the one or more captured digital media files, removing anyrestrictions configured to prevent a particular captured image frombeing stored locally on client device 105 and/or on servers 112 atservice/data provider 110; removing any restrictions configured toprevent a particular captured image from being transmitted to anotherdevice or storage medium; and/or removing any restrictions configured toprevent a particular captured image from being uploaded to a cloud-basednetworking entity, e.g., a social networking service. Thus, block 420may refer to rendering component 230 rendering the one or more captureddigital media files with at least one unobfuscated facial image.

Thus, FIG. 4 shows an example process for protecting the privacy ofsubjects captured in a digital media file who have not grantedpermission to have their facial images stored or published in a publicforum.

FIG. 5 shows an alternative example processing flow 500 for implementingdigital media privacy protection, arranged in accordance with at leastsome embodiments described herein. Processing flow 500 may includesub-processes executed by various components that are part of clientdevice 105 and/or service/data provider 110. However, processing flow500 is not limited to such components, as obvious modifications may bemade by re-ordering two or more of the sub-processes described here,eliminating at least one of the sub-processes, adding furthersub-processes, substituting components, or even having variouscomponents assuming sub-processing roles accorded to other components inthe following description. Processing flow 500 may include variousoperations, functions, or actions as illustrated by one or more ofblocks 505, 510, 515, and/or 520. Processing may begin at block 505.

Block 505 (Capture Digital Image) may refer to image capturing component210 on client device 105 capturing at least one digital media file,including at least one still photograph and/or one or more video files,which may or may not include one or more of subjects 102. Processing mayproceed from block 505 to block 510.

Block 510 (Compare Facial Images to Privacy Policy) may refer to facialrecognition component 220 discerning any facial image within the one ormore digital media files captured by image capturing component 210 forcomparison against facial images included in a locally stored databaseof facial images, i.e., data 111 as accessed by policy component 225.Facial recognition component 220 may recognize and compare thediscernible facial images from the photograph or video image framecaptured by image capturing component 210. Block 415 may further includepolicy component 225 accessing data 111 stored at client device 105and/or service/data provider 110 to determine whether a particularfacial image included in the captured photograph or video file that isdiscerned by facial recognition component 220 corresponds to any of theaffirmative, i.e., authorized, privacy policies for various ones ofsubjects 102. Processing may proceed from block 510 to block 515.

Block 515 (Obfuscate Facial Images Not Included in Privacy Policy) mayrefer to obfuscation component 215 obfuscating, or otherwise blurring,at least all discernible facial images included in the one or moredigital media files captured by image capturing component 210 for whichan affirmative, i.e., authorized privacy policy is not included in data111. Thus, in accordance with one or more alternative embodiments ofdigital media privacy protection, any facial image in the one or morecaptured digital media files having discernible features may beunobfuscated until it is determined that there is no correspondingaffirmative privacy policy. Processing may proceed from block 515 toblock 520.

Block 520 (Render Captured Image File) may refer to rendering component230 rendering the one or more captured digital media files with anunobfuscated facial image for each of subjects 102 for whom anaffirmative privacy policy is included in data 111.

Thus, FIG. 5 shows an alternative example process for protecting theprivacy of subjects captured in a digital media file by obfuscatingthose for whom authentication has not been actively granted.

FIG. 6 shows a block diagram illustrating an example computing device600 by which various example solutions described herein may beimplemented, arranged in accordance with at least some embodimentsdescribed herein.

More particularly, FIG. 6 shows an illustrative computing embodiment, inwhich any of the processes and sub-processes described herein may beimplemented as computer-readable instructions stored on acomputer-readable medium. The computer-readable instructions may, forexample, be executed by a processor of a mobile unit, a network element,and/or any other computing device, particularly as applicable to theapplications and/or programs described above corresponding to theconfiguration 100 for digital media privacy protection.

In a very basic configuration, computing device 600 may typicallyinclude one or more processors 604 and a system memory 606. A memory bus608 may be used for communicating between processor 604 and systemmemory 606.

Depending on the desired configuration, processor 604 may be of any typeincluding but not limited to a microprocessor (μP), a microcontroller(μC), a digital signal processor (DSP), or any combination thereof.Processor 604 may include one or more levels of caching, such as a levelone cache 610 and a level two cache 612, a processor core 614, andregisters 616. Processor core 614 may include an arithmetic logic unit(ALU), a floating point unit (FPU), a digital signal processing core(DSP Core), or any combination thereof. A memory controller 618 may alsobe used with processor 604; or in some implementations, memorycontroller 618 may be internal to processor 604.

Depending on the desired configuration, system memory 606 may be of anytype including but not limited to volatile memory (such as RAM),non-volatile memory (such as ROM, flash memory, etc.) or any combinationthereof. System memory 606 may include an operating system 620, one ormore applications 622, and program data 624.

Application 622 may include, e.g., a client application 626, that may bearranged to perform the functions for digital media privacy protection,which are described previously with respect to FIGS. 1-4. Program data624 may include a table 650, which may be useful for implementingactuation of appropriate components or modules as described herein. Forexample, table 650 may include catalog information regarding data storedin a local cloud-based service and data center, information regardingother cloud-based service and data centers associated with a particularcloud-based storage service, etc.

System memory 606 is an example of computer storage media. Computerstorage media may include, but not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disks (DVD)or other optical storage, magnetic cassettes, magnetic tape, magneticdisk storage or other magnetic storage devices, or any other mediumwhich may be used to store the desired information and which may beaccessed by computing device 600. Any such computer storage media may bepart of computing device 600.

The network communication link may be one example of a communicationmedia. Communication media may typically be embodied bycomputer-readable instructions, data structures, program modules, orother data in a modulated data signal, such as a carrier wave or othertransport mechanism, and may include any information delivery media. A“modulated data signal” may be a signal that has one or more of itscharacteristics set or changed in such a manner as to encode informationin the signal. By way of example, and not limitation, communicationmedia may include wired media such as a wired network or direct-wiredconnection, and wireless media such as acoustic, radio frequency (RF),microwave, infrared (IR) and other wireless media. The termcomputer-readable media as used herein may include both storage mediaand communication media.

Computing device 600, as described above, may be implemented as aportion of a small-form factor portable (or mobile) electronic devicesuch as mobile client or, alternatively, a personal data assistant(PDA), a personal media player device, a personal headset device, anapplication specific device, or a hybrid device that include any of theabove functions. Computing device 600 may also be implemented as apersonal computer including both laptop computer and non-laptop computerconfigurations.

There is little distinction left between hardware and softwareimplementations of aspects of systems; the use of hardware or softwareis generally (but not always, in that in certain contexts the choicebetween hardware and software can become significant) a design choicerepresenting cost vs. efficiency tradeoffs. There are various vehiclesby which processes and/or systems and/or other technologies describedherein may be implemented, e.g., hardware, software, and/or firmware,and that the preferred vehicle may vary with the context in which theprocesses and/or systems and/or other technologies are deployed. Forexample, if an implementer determines that speed and accuracy areparamount, the implementer may opt for a mainly hardware and/or firmwarevehicle; if flexibility is paramount, the implementer may opt for amainly software implementation; or, yet again alternatively, theimplementer may opt for some combination of hardware, software, and/orfirmware.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes for system configuration 100 via the use ofblock diagrams, flowcharts, and/or examples. Insofar as such blockdiagrams, flowcharts, and/or examples contain one or more functionsand/or operations, it will be understood by those within the art thateach function and/or operation within such block diagrams, flowcharts,or examples can be implemented, individually and/or collectively, by awide range of hardware, software, firmware, or virtually any combinationthereof. In one embodiment, several portions of the subject matterdescribed herein may be implemented via ASICs, Field Programmable GateArrays (FPGAs), digital signal processors (DSPs), or other integratedformats. However, those skilled in the art will recognize that someaspects of the embodiments disclosed herein, in whole or in part, can beequivalently implemented in integrated circuits, as one or more computerprograms running on one or more computers, e.g., as one or more programsrunning on one or more computer systems, as one or more programs runningon one or more processors, e.g., as one or more programs running on oneor more microprocessors, as firmware, or as virtually any combinationthereof, and that designing the circuitry and/or writing the code forthe software and/or firmware would be well within the skill of one ofskill in the art in light of this disclosure. In addition, those skilledin the art will appreciate that the mechanisms of the subject matterdescribed herein are capable of being distributed as a program productin a variety of forms, and that an illustrative embodiment of thesubject matter described herein applies regardless of the particulartype of signal bearing medium used to actually carry out thedistribution. Examples of a signal bearing medium include, but are notlimited to, the following: a recordable type medium such as a floppydisk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory,etc.; and a transmission type medium such as a digital and/or an analogcommunication medium (e.g., a fiber optic cable, a waveguide, a wiredcommunications link, a wireless communication link, etc.).

Those skilled in the art will recognize that it is common within the artto describe devices and/or processes in the fashion set forth herein,and thereafter use engineering practices to integrate such describeddevices and/or processes into data processing systems. That is, at leasta portion of the devices and/or processes described herein can beintegrated into a data processing system via a reasonable amount ofexperimentation. Those having skill in the art will recognize that atypical data processing system generally includes one or more of asystem unit housing, a video display device, a memory such as volatileand non-volatile memory, processors such as microprocessors and digitalsignal processors, computational entities such as operating systems,drivers, graphical user interfaces, and applications programs, one ormore interaction devices, such as a touch pad or screen, and/or controlsystems including feedback loops and control motors, e.g., feedback forsensing position and/or velocity; control motors for moving and/oradjusting components and/or quantities. A typical data processing systemmay be implemented utilizing any suitable commercially availablecomponents, such as those typically found in datacomputing/communication and/or network computing/communication systems.

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely examples, and that in fact many other architectures can beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled”, to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable”, to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents and/or wirelessly interactable and/or wirelessly interactingcomponents and/or logically interacting and/or logically interactablecomponents.

Lastly, with respect to the use of substantially any plural and/orsingular terms herein, those having skill in the art can translate fromthe plural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations may be expressly set forth herein for sakeof clarity.

It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims, e.g., bodies of theappended claims, are generally intended as “open” terms, e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc. It will be further understood by those within the art that if aspecific number of an introduced claim recitation is intended, such anintent will be explicitly recited in the claim, and in the absence ofsuch recitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to embodiments containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an,” e.g., “a” and/or “an” should be interpreted to mean “at least one”or “one or more;” the same holds true for the use of definite articlesused to introduce claim recitations. In addition, even if a specificnumber of an introduced claim recitation is explicitly recited, thoseskilled in the art will recognize that such recitation should beinterpreted to mean at least the recited number, e.g., the barerecitation of “two recitations,” without other modifiers, means at leasttwo recitations, or two or more recitations. Furthermore, in thoseinstances where a convention analogous to “at least one of A, B, and C,etc.” is used, in general such a construction is intended in the senseone having skill in the art would understand the convention, e.g., “asystem having at least one of A, B, and C” would include but not belimited to systems that have A alone, B alone, C alone, A and Btogether, A and C together, B and C together, and/or A, B, and Ctogether, etc. In those instances where a convention analogous to “atleast one of A, B, or C, etc.” is used, in general such a constructionis intended in the sense one having skill in the art would understandthe convention, e.g., “a system having at least one of A, B, or C” wouldinclude but not be limited to systems that have A alone, B alone, Calone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc. It will be further understood by those withinthe art that virtually any disjunctive word and/or phrase presenting twoor more alternative terms, whether in the description, claims, ordrawings, should be understood to contemplate the possibilities ofincluding one of the terms, either of the terms, or both terms. Forexample, the phrase “A or B” will be understood to include thepossibilities of “A” or “B” or “A and B.”

From the foregoing, it will be appreciated that various embodiments ofthe present disclosure have been described herein for purposes ofillustration, and that various modifications may be made withoutdeparting from the scope and spirit of the present disclosure.Accordingly, the various embodiments disclosed herein are not intendedto be limiting, with the true scope and spirit being indicated by thefollowing claims.

We claim:
 1. A method to manage privacy, the method comprising:maintaining, by a server, a database of a plurality of facial imagesassociated with one or more users, wherein the plurality of facialimages includes a first facial image associated with a first userpermission of a first user, wherein the first user permission indicatesa condition to obfuscate facial images of the first user; receiving, bythe server, a digital image from a client device; comparing, by theserver, a second facial image in the digital image with the first facialimage associated with the first user permission; determining, by theserver, based on the comparing, whether the second facial image needs tobe obfuscated; in response to a determination that the second facialimage needs to be obfuscated, instructing, by the server, the clientdevice to obfuscate the second facial image in the digital image; and inresponse to a determination that the second facial image does not needto be obfuscated, instructing, by the server, the client device to notobfuscate the second facial image in the digital image.
 2. The method ofclaim 1, wherein the condition includes a location.
 3. The method ofclaim 1, wherein the condition includes a time setting.
 4. The method ofclaim 1, wherein the condition includes one or more users for whompermission has been granted to access unobfuscated facial images of thefirst user.
 5. The method of claim 1, wherein the digital image includesa photograph or a video file.
 6. The method of claim 1, wherein theclient device is configured to perform at least one of storing,transferring, or sharing the digital image.
 7. A server, comprising: aserver policy component configured to: maintain a database of aplurality of facial images associated with one or more users, whereinthe plurality of facial images include a first facial image associatedwith a first user permission of a first user, wherein the first userpermission indicates a condition to render facial images of the firstuser; receive a digital image from a client device; compare a secondfacial image in the digital image with the first facial image associatedwith the first user permission; determine, based on the comparison,whether the second facial image can be rendered; in response to adetermination that the second facial image can be rendered, instruct theclient device to render the second facial image in the digital image;and in response to a determination that the second facial image cannotbe rendered, instruct the client device to not render the second facialimage in the digital image.
 8. The server of claim 7, wherein theinstruction of the client device to render the second facial image inthe digital image includes the server policy component being furtherconfigured to remove a restriction that prevents the digital image frombeing stored locally on the client device.
 9. The server of claim 7,wherein the instruction of the client device to render the second facialimage in the digital image includes the server policy component beingfurther configured to remove a restriction that prevents the digitalimage from being transmitted to another device.
 10. The server of claim7, wherein the instruction of the client device to render the secondfacial image in the digital image includes the server policy componentbeing further configured to remove a restriction that prevents thedigital image from being uploaded to a cloud-based networking entity.11. The server of claim 7, wherein the condition includes a location.12. The server of claim 7, wherein the condition includes a timesetting.
 13. The server of claim 7, wherein the condition includes oneor more users for whom permission has been granted to accessunobfuscated facial images of the first user.
 14. The server of claim 7,wherein the digital image includes a photograph or a video file.
 15. Anon-transitory computer-readable medium storing computer-executableinstructions that, in response to being executed, cause one or moreprocessors to execute operations comprising: maintaining, by a server, adatabase of a plurality of facial images associated with one or moreusers, wherein the plurality of facial images includes a first facialimage associated with a first user permission of a first user, whereinthe first user permission indicates a condition to obfuscate facialimages of the first user; receiving, by the server, a digital image froma client device; comparing, by the server, a second facial image in thedigital image with the first facial image associated with the first userpermission; determining, by the server, based on the comparing, whetherthe second facial image needs to be obfuscated; in response to adetermination that the second facial image needs to be obfuscated,instructing, by the server, the client device to obfuscate the secondfacial image in the digital image; and in response to a determinationthat the second facial image does not need to be obfuscated,instructing, by the server, the client device to not obfuscate thesecond facial image in the digital image.
 16. The non-transitorycomputer-readable medium of claim 15, wherein the condition includes alocation.
 17. The non-transitory computer-readable medium of claim 15,wherein the condition includes a time setting.
 18. The non-transitorycomputer-readable medium of claim 15, wherein the condition includes oneor more users for whom permission has been granted to accessunobfuscated facial images of the first user.
 19. The non-transitorycomputer-readable medium of claim 15, wherein the digital image includesa photograph or a video file.
 20. The non-transitory computer-readablemedium of claim 15, wherein the client device is configured to performat least one of storing, transferring, or sharing the digital image.